Skip to content

Bump pipe-fittings to v2.9.1 to fix GHCR plugin install auth error#4980

Merged
kaidaguerre merged 2 commits into
v2.1.xfrom
bump-pipe-fittings-v2.9.1-ghcr-fix
Apr 22, 2026
Merged

Bump pipe-fittings to v2.9.1 to fix GHCR plugin install auth error#4980
kaidaguerre merged 2 commits into
v2.1.xfrom
bump-pipe-fittings-v2.9.1-ghcr-fix

Conversation

@kaidaguerre
Copy link
Copy Markdown
Contributor

Summary

Risk

The bump crosses pipe-fittings v2.7.x and v2.8.x, which include the lazy-loading parser work (#773). That code has been running in production in powerpipe v1.5.1 (pipe-fittings v2.9.0) since 2026-04-07, so this is not a first-mover change.

Steampipe does not load mods/workspaces, so the only part of #773 that executes here is the parallel LoadFileData path in pipe-fittings/parse, which activates when >=4 .spc files are loaded.

Test plan

  • make build - clean
  • steampipe service start with 4 .spc files (parallel LoadFileData path)
  • steampipe query "select now(), current_date" - TIMESTAMPTZ + DATE display correct
  • steampipe plugin list - OCI layer intact
  • steampipe service stop - clean

pipe-fittings v2.9.1 adds an anonymous retry to OCI pulls when stored
GHCR credentials (from ~/.docker/config.json) are rejected. Without
this, an expired or revoked PAT causes `steampipe plugin install` to
fail with an opaque 403 even when the image is publicly pullable.

Also picks up the pipe-fittings dependabot security sweep and GH
Actions hardening included in v2.9.0.
…g workspace

The previous test fixtures referenced AWS account 632902152528 / alias
'nagraj-aaa', which no longer exist in the turbot-ops/clitesting test
workspace. Updating to account 097350876455 / alias 'turbot-silverwater'
to match the current workspace state.
@MichaelBurgess MichaelBurgess self-requested a review April 22, 2026 11:19
@kaidaguerre kaidaguerre merged commit bb35ed6 into v2.1.x Apr 22, 2026
28 checks passed
@kaidaguerre kaidaguerre deleted the bump-pipe-fittings-v2.9.1-ghcr-fix branch April 22, 2026 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants